-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sm/simplify-message-imports #358
Conversation
@@ -0,0 +1,101 @@ | |||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh, the actual rule that led to this PR
QA: (used 🟢 existing uses of import { dirname } from 'node:path';
import url from 'node:url';
Messages.importMessagesDirectory(dirname(url.fileURLToPath(import.meta.url))); |
This willl help roll it out everywhere.
@W-14626332@
CI 🔴 🟢 explanation:
the ones with
--fix
in the name are the "what would happen when devScripts runslint --fix
everywhere.the ones without
--fix
fail when any change would be made (helps verify the expected errors are thrown)packaging is green for both because it's not on ESM
This PR also moves the linter rules to eslint6 to align with everything else. There were some deprecations, including the method for getting sourceCode for the file, which is a lot of the PR noise.
the API changed some for the rule config (error, warn) => (recommended, strict, stylistic)
the imports/utils all got reorganized because (I think ESM, or at least module:node16 etc)